[docs] Add troubleshooting section for language support load failures in aspire new#1024
Open
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
…in aspire new Documents the improved diagnostics surfaced in microsoft/aspire#17311: - New error messages that list available languages when a specific language is not found - The binary-mismatch error message and guidance when no language support implementations are discovered at all - Resolution steps (aspire cache clear, checking the log for LoaderExceptions and version mismatch warnings) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
3 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a Troubleshooting section to the aspire new CLI command reference to help users diagnose and resolve language support / code generator load failures (typically caused by integration assembly version mismatches), aligning docs with the improved diagnostics in microsoft/aspire#17311.
Changes:
- Documents the updated “language support not found” error shapes (including the “no implementations discovered” case).
- Provides resolution steps (
aspire cache clear, then re-runaspire new) and guidance to inspect logs forLoaderExceptions/ version mismatch warnings. - Adds a tip for using
--log-level Debug/Traceto capture more detailed logs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+196
to
+197
| This usually indicates a binary mismatch between the bundled apphost server and the integration assemblies on disk; | ||
| check the apphost server log for 'LoaderExceptions' Warnings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents changes from microsoft/aspire#17311
Authored by
@IEvangelist.Targeting
release/13.4based on the source PR milestone13.4.Why this PR is needed
microsoft/aspire#17311 hardened the diagnostics for integration-assembly load failures in the
aspire newcode-generation path. Before this change, when a language support or code generator assembly failed to load its types, users saw only a bareNo language support found for: Xerror with no indication of the root cause.After the change:
LoaderExceptionswarnings and explains the likely binary-mismatch cause.Warning-level log entry names the offending assembly and the version mismatch (bundled vs. on-disk) to make self-diagnosis possible.Documentation changes
Added a Troubleshooting section to
src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdxthat:aspire cache clearfollowed by a freshaspire newrun.LoaderExceptionsorversion mismatchwarnings.--log-level Debugto capture a detailed log.Files modified
src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx— added Troubleshooting section (38 lines)